Messages

1

Hardware and Performance / Re: Advice on ditching USB nic or wait for better support

« on: January 19, 2019, 03:47:59 pm »

Can you check from the console? You'll be able to bring the WAN interface up and down and ping external hosts separately from getting your LAN up and running. I have hardly any Cisco experience, but I know that they can be slightly awkward. The first thing I would try is changing VLAN 1 on port 2 to be tagged, or remove it.

You may also want to put the modem aside for a moment and confirm that the trunk on port 2 works as you expect. E.g. connect a DHCP server on port 1 and confirm that the "WAN" interface on OPNsense picks up an IP address.

Bart...

Alright so finally I was able to setup a DHCP server and test the VLAN.
Directly when I plugged in a cable from my DHCP server to port 1 it lit up green and I received an IP address on my WAN interface.

So it must be my ISP or switch or a combination I guess..
Could it be spanning tree or some other function that I need to disable?

2

Hardware and Performance / Re: Advice on ditching USB nic or wait for better support

« on: December 01, 2018, 05:40:29 am »

I was faced with the same issue when changing from a dual NIC to a single NIC hardware platform. Instead of going for an external NIC, I opted for a VLAN setup.

You basically configure a WAN port and LAN port(s) on the switch, while you trunk both traffic streams down to OPNsense on its switch port as separate VLAN's. Added benefit is that you can further carve up your network; e.g. have a guest port that can only see the internet, or an IoT segment that is more strictly monitored.

While you can spend thousands on enterprise gear, VLAN capable switches don't need to cost the earth. Check out the TP-Link managed switches like the TL-SG105E.

Bart...

So I got a Cisco SG200-08 and created a VLAN 101 for WAN traffic.
Configuration:

Port 1: WAN Link (Cable from my modem)
Port 2: LAN Link (OPNSense)

Port 1: PVID 101, 101 Untagged
Port 2: PVID 1, 1 Untagged and 101 Tagged

Problem is that when I connect the WAN cable the switch still says Link Down even though the cable is connected.
Why? Sorry I'm a networking noob 

I have added the VLAN in OPNSense: Interfaces: Other Types: VLAN
And changed the WAN assignment to VLAN 101 in OPNSense Interfaces: Assignments

3

Hardware and Performance / Advice on ditching USB nic or wait for better support

« on: November 17, 2018, 02:51:02 pm »

So first before you start butchering me for running a USB nic.. We are talking about a home user here that used to run a crappy TP-Link router with OpenWRT.

I had serious issues with my previous router. Every streaming service was lagging and it was basically unusable.
So I had a J1900 based PC laying around (Q1900-ITX). Problem was that my case did not support external PCI-E cards so I could not add a nice Intel based Ethernet card to it.

Decided to give a USB nic a try since I only have 100Mbit down and 10Mbit up.
Got a RTL8153 Gigabit Ethernet USB3 Adapter and plugged it in. Works fine lag is gone but when I test my speed I only get 40Mbit down.

How could this be? USB3 is 5 Gbits right?

Code: [Select]

ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ugen0.3: <Realtek USB 101001000 LAN> at usbus0, cfg=1 md=HOST spd=SUPER (5.0Gbps) pwr=ON (64mA)

Anyway I'm prepared to get a new system with real nics, but it will probably be Realtek based too since I'm a home user and not willing to spend the big bucks...
Is it even worth it to buy a new system? I figure this is a driver issue and might be fixed in a newer freebsd release?