This may be a Linux answer, but it's more of a GNS3 question

wolverene13

I wasn't sure where to post this question because it involves Linux and GNS3, so I could have gone to a Linux forum or a Cisco/GNS3 forum, but I think that being that GNS3 is purely for Cisco (ok, so there's one Juniper device in GNS3, but whatever), I'll get more help here.

I have always used live equipment for labbing out my certs, but it's come to the point where I will have to either buy a 7200 or just use GNS3. I run Debian Lenny and have found all sorts of posts, web sites, and blogs on how to set it up, but none of them answer my question.

----I have configured my Linux server like this so that I can connect GNS3 via a cloud to my real Cisco lab at home:

allen@debian:~$ sudo tunctl -t tap1 -u allen
Set 'tap1' persistent and owned by uid 1000
allen@debian:~$ sudo ip l s dev tap1 up
allen@debian:~$ sudo brctl addbr br1
allen@debian:~$ sudo ip l s dev br1 up
allen@debian:~$ sudo brctl addif br1 tap1
allen@debian:~$ sudo brctl addif br1 eth0
allen@debian:~$ sudo ifconfig eth0 0.0.0.0 promisc
allen@debian:~$ sudo ifconfig tap1 0.0.0.0 promisc
allen@debian:~$ sudo ip a a 10.10.20.3/24 dev br1
allen@debian:~$ sudo ip r a default via 10.10.20.1

---

I have verified that br1 has tap1 and eth0 bridged together...

allen@debian:~$ sudo brctl show br1
bridge name bridge id STP enabled interfaces
br1 8000.0019d11ac752 no eth0 tap1
pan0 8000.000000000000 no

---

The server shows that br1 has the IP address I configured and a default route out...

allen@debian:~$ ip r
10.10.20.0/24 dev br1 proto kernel scope link src 10.10.20.3
default via 10.10.20.1 dev br1

---

All pertinent interfaces are up...

allen@debian:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 100
link/ether 00:19:d1:1a:c7:52 brd ff:ff:ff:ff:ff:ff
inet6 fe80::219:d1ff:fe1a:c752/64 scope link
valid_lft forever preferred_lft forever
3: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
4: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 8a:59:16:8f:c6:04 brd ff:ff:ff:ff:ff:ff
7: tap1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
link/ether 6a:7a:94:c3:26:2e brd ff:ff:ff:ff:ff:ff
inet6 fe80::687a:94ff:fec3:262e/64 scope link
valid_lft forever preferred_lft forever
8: br1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 00:19:d1:1a:c7:52 brd ff:ff:ff:ff:ff:ff
inet 10.10.20.3/24 scope global br1
inet6 fe80::e419:cbff:fe15:318c/64 scope link
valid_lft forever preferred_lft forever

---

The routing table sees the IPs...

allen@debian:~$ sudo route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.10.20.0 0.0.0.0 255.255.255.0 U 0 0 0 br1
0.0.0.0 10.10.20.1 0.0.0.0 UG 0 0 0 br1

---

Yet, I can't ping anything...

allen@debian:~$ ping 10.10.20.1
PING 10.10.20.1 (10.10.20.1) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C
--- 10.10.20.1 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5040ms

---

Nor can I traceroute...

allen@debian:~$ traceroute 10.10.20.1
traceroute to 10.10.20.1 (10.10.20.1), 30 hops max, 60 byte packets
send: Operation not permitted
allen@debian:~$ sudo traceroute 10.10.20.1
traceroute to 10.10.20.1 (10.10.20.1), 30 hops max, 60 byte packets
send: Operation not permitted
allen@debian:~$

---

What am I doing wrong???

mikej412

Firewall?

wolverene13

mikej412 wrote: »

Firewall?

Bingo! I shut off the firewall and it works!

allen@debian:~$ ping 4.2.2.2
PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
64 bytes from 4.2.2.2: icmp_req=1 ttl=56 time=24.5 ms
64 bytes from 4.2.2.2: icmp_req=2 ttl=56 time=16.3 ms
64 bytes from 4.2.2.2: icmp_req=3 ttl=56 time=17.1 ms
64 bytes from 4.2.2.2: icmp_req=4 ttl=56 time=17.8 ms
^C
--- 4.2.2.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 16.345/18.981/24.552/3.263 ms


*facepalm* I can't believe I didn't think of that!

Thanks Mike!