News: This forum is now permanently frozen.
Pages: [1]
Topic: Unable to configure m0n0 with Swisscom Centro Grande  (Read 1212 times)
« on: November 01, 2014, 09:54:34 »
echappatte *
Posts: 28

Hi all  Wink

Trying to go back to m0n0wall but even with doing my best I can't have anything working.

In the past, I used m0n0 on my Alix, then switched to pfSense (1.x and now 2.x) mainly to have scheduled task.
From 1.8.x this is included in m0n0, so tried to use this new version !

But I'am unable to configure m0n0 with the IP Passthrough functionality of Centro Grande (ADB Broadband V226N1W).
Same Centro Grande setup works fine with pfSense.
WAN interface is configured in DHCP.

I'am able to have the WAN IP on m0n0, but it's looks like there is no default gateway.
No DNS too, tried to put manually the ones of the Centro, not resolution.

Below my configuration, I only know "interface" menu and "ifconfig" exec command.
If someone can explain me how to view routing table ?

What's wrong with my setup ? I'am sure a lot of users have an awful swisscom router too ?
Any help will be much appreciated Smiley
Thanks

Code:
$ ifconfig
vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
ether 00:0d:b9:17:a1:90
inet6 fe80::20d:b9ff:fe17:a190%vr0 prefixlen 64 scopeid 0x1
nd6 options=43<PERFORMNUD,ACCEPT_RTADV,NO_RADR>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
vr1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
ether 00:0d:b9:17:a1:91
inet6 fe80::20d:b9ff:fe17:a191%vr1 prefixlen 64 scopeid 0x2
inet 176.127.111.xxx netmask 0xffffff00 broadcast 176.127.111.255
nd6 options=41<PERFORMNUD,NO_RADR>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
vr2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
ether 00:0d:b9:17:a1:92
media: Ethernet autoselect
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
nd6 options=43<PERFORMNUD,ACCEPT_RTADV,NO_RADR>
enc0: flags=41<UP,RUNNING> metric 0 mtu 1536
vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:0d:b9:17:a1:90
inet6 fe80::20d:b9ff:fe17:a190%vlan0 prefixlen 64 scopeid 0x6
inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255
nd6 options=41<PERFORMNUD,NO_RADR>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
vlan: 110 parent interface: vr0

Code:
WAN interface
Status up
DHCP up 
MAC address 00:0d:b9:17:a1:91
IPv4 address 176.127.111.xxx/255.255.255.0
ISP DNS servers 192.168.1.1
Media 100baseTX <full-duplex>
In/out packets 50/13 (7 KB/2 KB)
In/out errors 0/0
Collisions 0
« Reply #1 on: November 02, 2014, 03:03:25 »
Lee Sharp *****
Posts: 517

Can you stick a Linux box directly on there and show us what it is supposed to look like?  Not sure what the problem is as I do not know what it is supposed to be.
« Reply #2 on: November 02, 2014, 11:07:33 »
echappatte *
Posts: 28

Can you stick a Linux box directly on there and show us what it is supposed to look like?  Not sure what the problem is as I do not know what it is supposed to be.
Thank for your reply Smiley

You suggest I put a Linux at the place of m0n0 and I post outputs for IP config and routes ?
« Reply #3 on: November 03, 2014, 18:06:34 »
Lee Sharp *****
Posts: 517

Yes...  Or your data for psSense.  We can make it look like anything, but first we have to know what it is supposed to look like.  So any way you can get a known good config would help.
« Reply #4 on: November 04, 2014, 20:00:21 »
echappatte *
Posts: 28

Here are the interfaces config from working pfSense, WAN ip changed from first post :

Code:
$ ifconfig
vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
ether 00:0d:b9:17:a1:90
inet6 fe80::20d:b9ff:fe17:a190%vr0 prefixlen 64 scopeid 0x1
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
vr1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
ether 00:0d:b9:17:a1:91
inet 85.2.78.XXX netmask 0xffffff00 broadcast 85.2.78.255
inet6 fe80::20d:b9ff:fe17:a191%vr1 prefixlen 64 scopeid 0x2
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
vr2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
ether 00:0d:b9:17:a1:92
inet 192.168.11.1 netmask 0xffffff00 broadcast 192.168.11.255
inet6 fe80::20d:b9ff:fe17:a192%vr2 prefixlen 64 scopeid 0x3
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
enc0: flags=0<> metric 0 mtu 1536
pflog0: flags=100<PROMISC> metric 0 mtu 33192
pfsync0: flags=0<> metric 0 mtu 1460
syncpeer: 224.0.0.240 maxupd: 128 syncok: 1
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
vr0_vlan110: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:0d:b9:17:a1:90
inet6 fe80::20d:b9ff:fe17:a190%vr0_vlan110 prefixlen 64 scopeid 0x8
inet 192.168.10.1 netmask 0xffffff00 broadcast 192.168.10.255
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
vlan: 110 vlanpcp: 0 parent interface: vr0

Route :
Code:
IPv4
Destination Gateway Flags Refs Use Mtu Netif Expire
default 192.168.1.1 UGS 0 1730291 1500 vr1
85.2.78.0/24 link#2 U 0 0 1500 vr1
85.2.78.9 link#2 UHS 0 0 16384 lo0
127.0.0.1 link#7 UH 0 130 16384 lo0
192.168.1.1 00:0d:b9:17:a1:91 UHS 0 39082 1500 vr1
192.168.10.0/24 link#8 U 0 3119791 1500 vr0_vlan110
192.168.10.1 link#8 UHS 0 0 16384 lo0
192.168.11.0/24 link#3 U 0 131249 1500 vr2
192.168.11.1 link#3 UHS 0 0 16384 lo0

192.168.10.0/24 is my LAN subnet
192.168.1.0/24 is the "LAN" for Swisscom router, used in my case for SwisscomTV and guest WIFI.

Hope this can help to understand, if you need other informations let me know !

Thanks again for your help Smiley
« Reply #5 on: November 05, 2014, 01:02:03 »
Lee Sharp *****
Posts: 517

I think I get it.  Your WAN is multi-netted, and you need to see both the real IP stuff and the fake 192.168.0.1 stuff...  That is ugly.  I may need to think on that for a bit.
« Reply #6 on: November 05, 2014, 17:32:34 »
echappatte *
Posts: 28

Ok. I didn't realised that, but yeah, it's ugly.

But I don't have the choice, I can only set one "Pass-through" device in the Centro Grande.  This device is based on MAC Hostname or... IP. Lol
If I can set the device in "modem" rather than in "router" I would do it !

The only advantage of this is I still can manage the Centro Grande through pfSense...

Hope you have an idea, and I'm ready for testing.

Thanks for your help Smiley

PS : in the past, with m0n0 1.3.x and my older motorola router (with quite same pass-through functionality I think) it was working fine.
« Reply #7 on: November 05, 2014, 18:29:18 »
Lee Sharp *****
Posts: 517

If all you need is to manage it, get another nic and put it on wan but with a 192.168.0.1 address.  Or multinet the WAN.
« Reply #8 on: November 05, 2014, 21:06:17 »
echappatte *
Posts: 28

My first need is to have m0n0 working with Centro Grande in passthrough.
Then, if I can manage the Centro, it's nice.

I can't add NIC, I'am on an Alix board.
I can do all other things in configuration to achieve this, but I need explanations I think Wink
« Reply #9 on: November 06, 2014, 06:31:19 »
Lee Sharp *****
Posts: 517

With passthough set, it should just pull the IP address along with gateway and DNS.  Not sure why it is not...
« Reply #10 on: November 06, 2014, 17:37:40 »
echappatte *
Posts: 28

I can put another computer in DHCP with passthrough set to his MAC to seen what's happen ?
« Reply #11 on: November 07, 2014, 19:57:10 »
Lee Sharp *****
Posts: 517

No need to set the MAC. I doubt that is the problem.
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines