Forum Replies Created
The pc that you are trying to connect to the cisco switch has which IP,mask and gw? So far I don’t see anything wrong. Maybe you could post the firewall rules too.
What are the IPs, masks and gateways of each device?
You can always compile it and use the newer version, rather than the one found in ZS. There are instructions about building modules in ZS, follow them to get the compiling tools.
Then you had better not run DHCP server on ZS directly connected on the university network.
Are you sure the old bridge is just bridging the two network interfaces, rather than doing something else? The whole setup is pretty straight and the fact that it is not working makes me wonder if you are missing something. If you omit both the old bridge and the ZS and connect the laptop directly on the university network, does it work?
I am not sure for that.
-v 12d1 -p 140b
looks correct but maybe you need to pass some more arguments or create a config file. You need to search it a little bit more on the internet and practice with your usb.
It still is recognized as storage device rather than a modem. Try again with the usb_modeswitch.
That proves what I am saying about security. I suppose that the university requires you to acquire IP address via dhcp. Are you acquiring IP from their DHCP on your ZS? Maybe if you don’t get IP from their dhcp no traffic is allowed to your ZS.
When you plug in the usb, what is the output of
dmesg | tail -n 100
I had a look at that but was a little concerned about changing to bridge mode will the captive portal still work??
Nevermind about bridge mode. Stick to the QoS tutorial.
It also looks like you are not learning anything in the ARP table from the ETH00 interface. Maybe your university is blocking the MAC address of the ZS, or they are applying some kind of security, such as 802.1x .
Apart from that your configuration looks fine to me. You can try it by connecting two workstations on the two interfaces (in the same subnet) and see if they can ping each other.
can show you the available interfaces, so if you see any of them marked like
it most likely is a vlan subinterface.
Have you unplugged-plugged in the usb?
What is the output of the following?
ls -l /dev/ttyUSB*
Run these commands with usb plugged in.
First of all read the documentation and if you still have questions you can ask them here.
You have assigned 2 IP addresses in the BRIDGE00 that are in the same subnet. Either remove one or change one to be in another subnet.
As far as I know this is red hat linux based, correct? Try to add the vlan on the interface with the command
Usage: add [interface-name] [vlan_id]
set_flag [interface-name] [flag-num] [0 | 1]
set_egress_map [vlan-name] [skb_priority] [vlan_qos]
set_ingress_map [vlan-name] [skb_priority] [vlan_qos]
* The [interface-name] is the name of the ethernet card that hosts
the VLAN you are talking about.
* The vlan_id is the identifier (0-4095) of the VLAN you are operating on.
* skb_priority is the priority in the socket buffer (sk_buff).
* vlan_qos is the 3 bit priority in the VLAN header
* name-type: VLAN_PLUS_VID (vlan0005), VLAN_PLUS_VID_NO_PAD (vlan5),
DEV_PLUS_VID (eth0.0005), DEV_PLUS_VID_NO_PAD (eth0.5)
* bind-type: PER_DEVICE # Allows vlan 5 on eth0 and eth1 to be unique.
PER_KERNEL # Forces vlan 5 to be unique across all devices.
* FLAGS: 1 REORDER_HDR When this is set, the VLAN device will move the
ethernet header around to make it look exactly like a real
ethernet device. This may help programs such as DHCPd which
read the raw ethernet packet and make assumptions about the
location of bytes. If you don't need it, don't turn it on, because
there will be at least a small performance degradation. Default